翻訳と辞書
Words near each other
・ Continuous reactor
・ Continuous redial
・ Continuous revelation
・ Continuous scan laser Doppler vibrometry
・ Continuous signal
・ Continuous simulation
・ Continuous slowing down approximation range
・ Continuous spatial automaton
・ Continuous spectrum
・ Continuous spontaneous ventilation
・ Continuous stationery
・ Continuous stirred-tank reactor
・ Continuous stochastic process
・ Continuous subscription service
・ Continuous symmetry
Continuous test-driven development
・ Continuous testing
・ Continuous tone
・ Continuous Tone-Coded Squelch System
・ Continuous track
・ Continuous training
・ Continuous transmission mode
・ Continuous truss bridge
・ Continuous wave
・ Continuous wavelet
・ Continuous wavelet transform
・ Continuous wound infiltration
・ Continuous-flow intersection
・ Continuous-flow manufacturing
・ Continuous-repayment mortgage


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Continuous test-driven development : ウィキペディア英語版
Continuous test-driven development

Continuous test-driven development (CTDD) 〔Madeyski, L. and Kawalerowicz, M. ''Continuous Test-Driven Development - A Novel Agile Software Development Practice and Supporting Tool'', Proceedings of the 8th International Conference on Evaluation of Novel Approaches to Software Engineering (ENASE), 2013, Angers, France, 4–6 July 2013: p.260-267.〕 is a software development practice that extends test-driven development by means of automatic test execution in the background (sometimes called continuous testing〔Saff, D. and Ernst, M. D. ''Reducing wasted development time via continuous testing'', Fourteenth International Symposium on Software Reliability Engineering, 2003, Denver, USA, 17-20 November 2003: p.281-292.〕). In CTDD the developer writes a test first but is not forced to execute the tests manually. The tests are run automatically by a continuous testing tool (see external links for examples) running in the background. This technique can potentially reduce the time waste resulting from manual test execution by eliminating the need for the developer to start the test after each phase of the normal TDD practice: after writing the (initially failing) test, after producing the minimal amount of code for the test to pass and after refactoring the code. It can potentially reduce the time waste resulting from manual test execution.
== See also ==


抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Continuous test-driven development」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.